Release 10.1A: OpenEdge Development:
Translation Manager

Defining text as untranslatable

When creating OpenEdge applications, a developer can explicitly use the :U character-string literal after a text phrase to mark the text phrase as “Untranslatable.” For example, the developer might not want to translate the name of your company or the name of a product, an internal key value, or a string used in determining program behavior. The developer can use the :U notation to ensure that the Translation Manager will not even display a given text phrase in the list of phrases to be translated.

It is imperative that you mark any programmatic strings in you code withe the :U attribute that may be evaluated by the translation process. For example, perhaps you want to find message strings in your code that are displayed by IF THEN ELSE statements to translate. Now assume that some of the IF THEN ELSE statements use strings as part of the condition. You must add the :U attribute to these conditional strings to prevent them from being affected by the translation process.

When you extract text phrases in Translation manager, the Compiler automatically filters out and does not extract those phrases marked :U. You do not have to set this filter in the Translation Manager. You should encourage the developers to use the :U character string literal appropriately to make the task of selecting filters easier. See OpenEdge Development: AppBuilder for more information on filters.